OPENING QUESTIONS: How are:
fields
records
tables
related?
How are they different?
What type of data would fit nicely into a field tracking a user's age?
What type of data would fit nicely into a field tracking the price of an item?
How many fields would you use to track a person's name?
OBJECTIVES:
I will work to create a learning target spreadsheet during today's class
I will review my hack/attack presentation with Mr W during today's class
WORDS FOR TODAY:
- Big Data - a broad term for datasets so large or complex that traditional data processing applications are inadequate.
- Moore's Law - a predication made by Gordon Moore in 1965 that computing power will double every 1.5-2 years, it has remained more or less true ever since.
- Field - A holder of unique data of a unique data type (For example an AGE field contains integer data that stores a person's age. A field named FNAME would store character data that stores a person's first name
- Record - A "Row" of data related to a specific topic. For example FNAME, LNAME, ADDRESS, CITY, STATE, ZIP would contain data relating to a specific person.
- Table - A "Table" of data contains a bunch of rows of data. For example a spreadsheet is a table of data.
- Data Types: ?
WORK O' THE DAY:
The first step we take in designing a database is to design and name the fields that hold the discreet data in a database record.
Before the break we talked a wee bit about making a database record to track the members of a classroom.
The record contains the specific information about each student. The record is named in a way that makes it obvious the type of data contained in that record: Students
Each field contains data related to a specific part of the overall data.
- Each field is named in such a way to indicate the type of data contained in that field.
- Each field MUST be given a data type. If the data type is text then we must also define the width of the field.
For example:
Field Name |
Field Type |
Size (if Text) |
| StudentID |
Long Integer |
N/a |
| Fname |
Text |
50 |
| Lname |
Text |
50 |
| Address |
Text |
75 |
| City |
Text |
50 |
| State |
Text |
2 |
| Zip |
Text |
10 |
| Age |
Integer |
N/a |
| Club Member |
Boolean |
N/a |
| Account Balance |
Decimal or Floating Point or Currency |
N/a |
| Bday |
Date |
N/a |
Why is it considered appropriate database practice to use those particular data types? Please discuss.
Now we'll put that to the test -- please grab a big ol' sheet of butcher paper and I'll have you design your own database record.